1.7.1. Outline why documentation is needed at each stage of the systems life cycle.

external image documentation.jpg
The documentation, more specifically, the system documentation will include any details on how the system was designed and developed. Documentation is needed at each stage of the system life cycle to mainly make the job of the systems analyst currently working on the system and any other which, in the future will work on the system, easier.



1.7.2. Explain the features of documentation for design, programming and maintenance, that is, system documentation.

stack_of_documents.jpg
System Documentation: System documentation is written to help other system analyst who at a laterpoint in time might be hired to update the system. Technical documentation consists of:
  • details of the hardware and software required
  • details of data structures
  • details of expected inputs
  • data validation/verification methods
  • details of how data is processed
  • diagrams of how the data moves through the system
  • flowcharts describing how the system works.


1.7.3. Explain the features of documentation for the user, that is, user documentation.

289959683_f34d81f211.jpg


User documentation is written to help the user of the new system work with the new system and how to fix any problems. User documentation usually contains FAQ (Frequently Asked Questions), minimum and recommended system requirements, how to use the system's features, any error messages which might appear and a troubleshooting guide.


Best content in StJulians_ComputerScience | Diigo - Groups